Repository navigation
Log in to Postman CLI on every Codespace start - #12
Merged
Merged
Conversation
Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
post-create.shinto.devcontainer/postman-login.sh, run viapostStartCommand, so the CLI is logged in on every Codespace start, including restarts.postman login --with-api-key "$POSTMAN_API_KEY"and shows the real error if login fails.Setup
Add
POSTMAN_API_KEYas a Codespaces secret with access to this repo. If it is missing, the script prints a message and the user can log in manually.Testing
Not yet run in a Codespace. Both scripts pass
bash -n, andpostman-login.shprints the expected message when the key is unset.Generated with Claude Code